This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
With repeating meetings when you first create a recurring meeting there is a parent document and a response document.
When you make a change to an instance of a meeting you break out the response document into multiple documents with the $REF pointing to the parent document.
Some date / time fields in the parent and response documents need to stay in synch with the original date / time of the meeting while other fields get updated with the new date / time values.
If a single recurring response document has 5 repeating instances in it and you update say the 3rd one here is what you should do:
* Instances 1 and 2 stay in the original response document.
* Instance 3 gets put into a new response document.
* Instances 4 and 5 get put together in a new response document
* The $REF for each document should point to the parent document.
I wrote a Lotus Notes email & calendaring application using C/C++ and I can tell there's lots & lots of rules regarding creation and changes to recurring meetings.
It's a fairly complete listing of the Lotus Notes calendaring schema, what fields you need to set and when, and what values should be put into the various fields.